HFIR Single Crystal Reduction Interface¶

Set up reduction¶

The first step to reduce data with 4-Circle GUI is to set up the reduction environment. Reduction cannot work correctly if this step is SKIPPED.

1. Go to tab Setup & Data Access;
2. Set up Data Directory and Working Directory;
3. An alternative way to step 2 is to push button Load Default;
4. Push button Apply. Mantid thus checks whether the setup, including source data file’s URL, data directory and working directory are valid. Be noticed that the check of URL may return timeout error. It might be a false alarm. You might push the Apply button few more times.

Experiment overview¶

Usually if it is the first time to reduce data for an experiment, it is recommended to go through the whole experiment to gather some information.

1. Go to tab Survey;
2. Set up experiment number on the top of application window;
3. Input the range of the scan numbers for survey. Leaving them blank will result in going through all scans of the experiment;
4. Click button Survey;
5. It might take a while to load and scan all the SPICE files belonged to an individual experiment. After it is finished, the result will be shown in the table.
6. Save the survey result for future by clicking button Save;
7. Select a row, and click button View Peak, application will switch to tab View Raw Data automatically and set the scan and Pt number from the selected row.

Workflow to calculate and refine UB matrix¶

Here is a typical use case to calculate UB matrix after initial setup.

1. User specifies Experiment and pushes button Set
2. Users may do a new survey or load a survey result file in tab Survey;
3. User enters tab View Raw Data and inputs scan number and list all the measuring points (Pt.)
4. User views all the measurements
   • User finds out the measurement with the strongest reflection and push button use
   • Alternatively, user can use the survey result to find out the Pt. with the maximum counts of the scan
5. GUI shifts to tab Calculate UB automatically
6. User pushes button Find Peak with checking Load HKL from file
7. GUI finds the peak center and load HKL
8. User pushes button Add peak to add the peak to table
9. User repeats step 2 to 9 to add other peaks
10. User select the peaks that are linearly independent and pushes Calculate UB
11. GUI calculates UB matrix and show the result
12. User may push Index peak to use the calculated UB matrix to index peaks in the table to check UB matrix;
13. User may refine the UB matrix and thus lattice parameters
    1. user adds more peaks to the UB peak table;
    2. user selects at least 3 non-degenerate peaks;
    3. user clicks button Refine;
    4. application refines UB matrix and outputs the refined UB matrix, refined lattice parameters and their error.

Workflow to merge measurements in scan¶

Here is a typical use case to merge all the measuring points (Pt.) in a scan

1. User specifies Experiment and pushes button Set
2. User enters tab Merge Scan
3. User specifies the UB matrix either by From tab Calculate UB or by entering the values to text editor
4. User pushes button Set
5. User specifies the frame in which the merged data will be in. If the target frame is Q-Sample-Sapce, then there is no need to specify UB matrix
6. User specifies the scan numbers and push button Add
7. User specifies the base name for the output MDEventWorkspaces
8. User pushes button Process
9. User goes to MantidWorkbench to view the merged scan by SliceView

Workflow to calculate peak intensity of a single measurement scan¶

It is a common practice to have one measurement in a scan for a peak. The only reason to do so is that the signal is too weak for users to have enough beam time to have multiple measurements in a single peak’s scan. Therefore, it is not straight forward to calculate peak intensity from this type of measurement.

1. A user specifies the range of scan numbers that include all the neutron peaks regardless whether they are single-point measurement or multiple-points measurement.
2. The user pushes button Survey. Mantid will load all the SPICE files of the scans.
3. The users selects All single-point-measurement scans by checking Single Pt Scans.
4. The user launches single-point peak integration window from menu Peak Integraton and sub menu Single Pt Integration. Mantid will add all the single-point scans to the popped out window.
5. The user will be prompted with the information about how to map single-point scan to a complete nuclear peak scan with same 2theta.
6. The user may load a CSV file to which integrated peak table was exported previously.
7. The user pushes button Retrieve FWHM. Mantid then will gather FWHM value from integrated peak.
8. The user add mapped scans for each single-pt scan to peak processint tab, and integrate peaks.
9. The user pushes Retrieve FHWHM again to make sure every scan to have an FWHM.
10. The user pushes Integrate to integrate peaks.
11. The user pushes Export to Table to add the integrated peaks to peak processing table for final output.

Peak Integration with automatic background subtraction by approximation¶

This is an easy approximation to integrate a peak with background subtraction by specified region of interest.

The pre-requisit is that all events are normalized by monitor counts and scaled up by same factor (e.g, 1500).

1. Set up region of interest
   • define region of interest on the detector
   • check whether the ROI does not exclude any peak
2. Specify background Pts.
   • specify the Pts. in the scan that are used to estimate background
3. Integrate peaks
   • select peaks to integrate
   • integrate peaks
4. Review the integration result
5. Export to Fullprof peak integration (.int) file.

Converting SPICE UB matrix to Mantid UB matrix¶

Assuming that SPICE UB matrix (3 x 3) is composed as

• R11, R12, R13
• R21, R22, R23
• R31, R32, R33

Then, converted to UB matrix in Mantid, it is like

• R11, R12, R13
• R31, R32, R33
• -R21, -R22, -R23

Normalization¶

Counts of neutron on any detector shall be normalized by its corresponding monitor count and then be multiplied by a constant specified by user.

But for HB3A, the normalization to counting time is more reliable because the beam monitor may be unstable.

Region of interest¶

A region of interest (ROI) on the detector can be defined for each scan. The signals in the ROI of each Pt. in a scan construct a 3-dimensional diffraction peak.

The purpose to define the region of interest on detector is to reduce the affect of background noise.

Integration algorithm 1: simple counts summation¶

This algorithm is also called simple cuboid integration, which is to approximate the integrated peak intensity.

Measuring one peak usually contains around 20 Pt. in a same scan. In most of the cases, the first and last several measurements (called as Pt in SPICE) are background. Therefore, the background for per measurement can be estimated by averaging the summed number of counts normalized by either monitor counts or measuring time.

The integrated peak intensity is

where

• \(C_i\) is the normalized detector counts in ROI of measurement i
• \(\Delta X\) is the motor step
• \(B_i\) is the estimated background

The error can be calculated as

Integration algorithm 2: simple counts summation with fitted background¶

This algorithm is based on previous algorithm. It is assumed that if the statistic of the diffraction peak is good enough, then the curve, i.e., moving motor position against normalized counts, can be fitted with a Gaussian plus flat background.

where

• x is the (moving) motor position
• C is the normalized counts in ROI when the moving motor is at x

The integrated peak intensity and its error will be calculated as

where

• \(C_i\) is the normalized detector counts in ROI of measurement i
• \(\Delta X\) is the motor step
• \(B_i\) is the estimated background
• the set of measurements <pt> is defined by the motor positions in the range of \(x_0 \pm \frac{N}{2}FWHM\).
  • usually the default value of N is set to 2.
  • \(FWHM = 2\sqrt{2\ln2}s \approx 2.3548s\)

The error can be calculated as

Integration algorithm 3: calculate intensity from fitted model¶

It is assumed that for a well measured diffraction peak, in 3D, the counts in ROI of each measurement from the edge of the peak to the other edge of peak against the moving motor’s positions should be represented by a Gaussian function with flat background

Then the peak intensity should be the integral of the Gaussian from \(-\inf\) to \(+\inf\), i.e.,

The error of the intensity should be calculated by the propagation of fitted error of A and s.

Other peak integration algorithms in consideration¶

There are some other peak integration algorithms that we discussed. None of them has been implemented. But it is still worth to document them here.